src/molecules/ApplicationIcon/ApplicationIconCollection.tsx:178

• The tests at lines 135-144 and 155-161 import and reference fallback from ApplicationIconCollection, but this export has been removed in this PR. These tests will fail because fallback is no longer available. The tests need to be updated to reflect the new fallback behavior that generates acronyms from names instead of using a static icon.

export const bravos: IconDataWithColor[] = [
  {
    name: 'bravos1',
    prefix: 'bravos',
    height: '24',
    width: '24',
    color: '#99C6C9',

src/molecules/ApplicationIcon/ApplicationIconCollection.tsx:178

• The fallback export has been removed from ApplicationIconCollection, but it's still being imported in ApplicationIcon.test.tsx (line 9) and used in test assertions (lines 142, 160). This will cause test failures. The tests need to be updated to work with the new name-based fallback approach that no longer uses a static icon.

export const bravos: IconDataWithColor[] = [
  {
    name: 'bravos1',
    prefix: 'bravos',
    height: '24',
    width: '24',
    color: '#99C6C9',

src/molecules/ApplicationIcon/ApplicationIconCollection.tsx:179

• Removing the fallback export from ApplicationIconCollection will break existing tests. The ApplicationIcon.test.tsx file (lines 9, 142, 160) imports and uses fallback.svgPathData to verify fallback rendering behavior.

Since the fallback icon is now dynamically generated based on the application name rather than using a fixed icon, the tests need to be updated to either verify the text-based acronym rendering or use a different approach to test the fallback behavior.

export const bravos: IconDataWithColor[] = [
  {
    name: 'bravos1',
    prefix: 'bravos',
    height: '24',
    width: '24',
    color: '#99C6C9',
    svgPathData:

• .idea/vcs.xml: Language not supported

src/molecules/ApplicationIcon/ApplicationIconBase/ApplicationIconBase.tsx:113

• The iconData prop is now optional (since it can be either iconData or name), but ApplicationIconBase.tsx doesn't validate that at least one of these props is provided. If neither iconData nor name is passed, the component will render an empty container. Consider adding runtime validation or updating the type definition to enforce that one of these props must be provided.
  .idea/vcs.xml:12
• The .idea/vcs.xml file is an IDE-specific configuration file that is typically included in .gitignore. This file should not be committed to the repository as it's specific to IntelliJ IDEA/WebStorm and can vary between developers. Consider removing this file from the PR and adding .idea/ to your .gitignore if it's not already there.

• .idea/vcs.xml: Language not supported

src/molecules/ApplicationIcon/ApplicationIconBase/ApplicationIconBase.tsx:105

• ApplicationIconBaseProps extends Required, which makes size, iconOnly, withHover, and grayScale required. However, the component destructuring provides default values (size = 48, grayScale = false) and the FallbackProps interface extends AppIconProps (not Required), which makes these properties optional. This type mismatch could cause TypeScript errors when passing Fallback props to ApplicationIconBase. Consider making ApplicationIconBaseProps extend AppIconProps instead of Required, since the component already handles defaults.
  src/molecules/ApplicationIcon/ApplicationIconBase/ApplicationIconBase.tsx:70
• The hover styles only apply to SVG and div elements, but fallback icons now render a Typography component (p element) instead of an SVG. The hover animation won't apply to the text acronym, creating an inconsistent user experience between custom icons and fallback icons when withHover is true. Consider adding hover styles for the paragraph element or wrapping it in a way that the existing styles apply.